IBM Books

8371 Interface Configuration

Configuring Change Management

This chapter describes the Change management configuration commands. It includes the following sections:

Accessing the Change Management Configuration Environment

To enter the change management configuration command environment, use the CONFIG boot command. When the device's software is initially loaded, it is running in the OPCON process, signified by the * prompt. From the * prompt:

  1. Enter talk 6.
  2. At the Config> prompt, type boot.

To return to the CONFIG process, type exit.

Change Management Configuration Commands

This section describes the Change Management Configuration commands. Each command includes a description, syntax requirements, and an example. Table 18 summarizes the Change Management Configuration commands.

After accessing the Change Management Configuration environment, enter the configuration commands at the Boot config> prompt.

Table 18. Change Management Configuration Commands
Command Function
? (Help) Displays all the commands available for this command level or lists the options for specific commands (if available). See "Getting Help".
 Add   Adds an optional description to a configuration file. 
 Copy   Copies boot files and configuration files to or from banks. 
 Describe   Displays information about the stored loadfile images. 
 Erase   Erases a stored image or a configuration file. 
 List   Displays information about configuration files and scheduled load information. 
 Lock   Prevents the device from overwriting the selected configuration with any other configuration. 
 Set   Selects code bank and configuration to be used. 
 Tftp   Initiates TFTP file transfers between the IBM 8371 and remote servers. 
 Unlock   Removes the lock from a configuration allowing the configuration to be updated by the device. 
Exit Returns you to the previous command level. See "Exiting a Lower Level Environment".

Add

Use the add command to add an optional description to a configuration file.

Syntax:

add

Example: Boot config> add 

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 01:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:30 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
Select the source bank:  (A, B): [A] 
Select the source configuration:  (1, 2): [1] 1
Enter the description of the file: () New config for
today
 
Attempting to set description for bank A configuration 1.
Operation completed successfully.
 
 
Boot config>list
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for today          | 01 Jan 1970 00:58 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked

Copy

Use the copy command to copy configuration files and load images to and from the banks.

Syntax:

copy
configuration file

 
load image

Example:

Example: Boot config>copy 

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - CORRUPT        |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 01:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Select the source bank:  (A, B): [A]
Select the source configuration:  (1, 2): [1]
Select the destination bank:  (A, B): [B]
 
Select the destination configuration:  (1, 2): [1]
Copy SW configuration from: bank A, configuration 1
                         to: bank B, configuration 1.
 
Operation completed successfully.

If the copy fails you may receive one of the following messages:

Error: Active bank cannot be overwritten or erased.
You attempted to copy a configuration into the bank currently in use by the IBM 8371.

Error: File copy failed.
This condition occurs when the copy operation fails for reasons other than copying to the active configuration. The most common cause is specifying the same source and destination configurations. When you list (see "List") the configurations, CORRUPT appears next to the bank that is damaged.

Describe

Use the describe command to display information about a stored image.

Syntax: describe

Example: Boot config>describe 

+-------------------------+-------------------------+
|         BANK A          |         BANK B          |
| Product ID -   8371     | Product ID -   8371     |
| Version   4 Release   0 | Version   4 Release   0 |
| Mod       0 PTF       0 | Mod       0 PTF       0 |
| Feat.  2822 RPQ       0 | Feat.  2822 RPQ       0 |
| Date        31 Dec 1996 | Date        31 Dec 1996 |
+-------------------------+-------------------------+

Erase

Use the erase command to erase a configuration file.

Syntax:

erase
configuration [file]

 
load [image]

config or load
Erases a configuration file or a load image. Enter the config number to be erased after the erase command.

Example: Boot config>erase configuration 

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Select the source bank:  (A, B): [A] A
Select the configuration to erase:  (1, 2,): [1]2
Erase SW configuration file from bank A, configuration 2.
 
Operation completed successfully.
 
 
Boot config>list
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                |                   |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:14 |
| CONFIG 2 - NONE        | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked

Notice that the list command displays NONE by bank A, config 2.

If the erasure fails, a message indicating the failure appears on the console with the banks that failed.

List

Use the list command to display information about which load images and configuration files are available and active. This command may also be used to display boot options and scheduled load information.

Syntax:

list
 

Example: Boot config>list 

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - AVAIL          |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 01:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-----------------+
  * - Last Used Config      L - Config File is Locked
  
Boot config>

The possible file status descriptors are:

ACTIVE
The file is currently loaded and is running on the 8371

AVAIL
This is a valid file that can be made ACTIVE.

CORRUPT
The file was damaged or not loaded into the 8371 completely. The file must be replaced.

LOCAL
The file will be used only on the next reload or reset. After the file is used, it will be placed in AVAIL state.

PENDING
This file will be loaded on the next reload, reset, or power-up of the 8371.

Lock

Use the lock command to prevent the device from overwriting the selected configuration with any other configuration.

Syntax:

lock
 

Example: Boot config>lock 

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 01:03 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
Select the source bank:  (A, B): [A]
 
Select the source configuration:  (1, 2): [1] 2
Attempting to lock bank A and configuration 2.
 
Operation completed successfully.
 
 
Boot config>list
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:13 |
| CONFIG 2 - AVAIL   L   | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                |                   |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
Note:Note that bank A config 2 is marked with an "L."

Set

Use the set command to select the code bank and the configuration to use.

Syntax:

set
 

Example: Boot config>set 

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 01:03 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:13 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Select the source bank:  (A, B): [A] b
Select the source configuration:  (1, 2, 3, 4): [1] 2
Select the duration to use for booting:  (once, always): [always]
Set SW to boot using bank B and configuration 2, always.
 
Operation completed successfully.
 
 
Boot config>list
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:13 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - ACTIVE      |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked

TFTP

Use the tftp command to initiate TFTP file transfers between the 8371 and remote servers.

Syntax:

tftp get
config

load

tftp put
config

load

Example: Boot config>tftp get load 

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 01:03 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:01 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Specify the server IP address (dotted decimal): : [1.2.3.4] 192.9.200.1
Specify the remote file name: : (/u/bin) /usr/8371load/8371.img
Select the destination bank:  (A, B, F): [A] a
  TFTP SW load image
  get:   /usr/8371load/8371.img
  from:  192.9.200.1
  to:    bank A.
 
Operation completed successfully.

Notes:

    When putting files to a server:

  1. Make sure that the files on the target server have the appropriate permissions that would allow anyone to write to those files. If not, the put operation will fail.

  2. You must be aware of the files you are putting to the target server.

Unlock

Use the unlock command to allow the device to overwrite the selected configuration that was previously locked.

Syntax:

unlock
 

Example: Boot config>unlock 

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 01:03 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:13 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL   L   |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Select the source bank:  (A, B): [A] B
Select the source configuration:  (1, 2): [1] 2
Attempting to unlock bank B and configuration 2.
 
Operation completed successfully.
Boot config>list
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                |                   |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:01 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
Note:Note that bank A config 2 is no longer marked with an "L."

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]